Alarm correlation system

ABSTRACT

Network applications rely on ever-increasing diverse and complex transport service mechanisms. A transport service between points in a network often traverses multiple technologies involving numerous containments and adaptations. A network event affecting the transport service may occur in any number of elements supporting the transport service, resulting in a myriad of alarms. Prior techniques for suppressing alarms involving complex network information models and coding logic to reduce the number of alarms presented, but require additional steps before the network event can be troubleshot and resolved. In contrast, the provided alarm correlation technique presents a highly structured and comprehensive visual presentation depicting the network event affecting the transport service in terms of the supporting elements affected by the network event. The provided visual presentation enables a viewer to visually correlate the network event affecting the transport service with the transport service affected by the network event directly.

BACKGROUND OF THE INVENTION

Network management refers generally to maintaining and administratinglarge-scale computer or telecommunications networks at a top level ascontrasted with element management (intermediate level) and networkelement management (low level). Network management may be divided intoseparate management categories based on management tasks, such as fault,configuration, accounting, performance, and security. Fault managementin particular refers to recognizing, isolating, correcting and loggingfaults or other network events which have a negative significance, whichoccur in a network.

SUMMARY OF THE INVENTION

A method or corresponding apparatus in an example embodiment of thepresent invention represents a transport service between point A andpoint Z in a network in terms of physical network elements, networkentities within the physical network elements, and connections betweenthe network entities to form a representation of the transport service.The formed transport service representation shows intra-network elementconnections, inter-network element connections, and relationshipsbetween the network entities. The method or corresponding apparatus alsorepresents a network event affecting the transport service to form arepresentation of the network event. The method or correspondingapparatus simultaneously presents the network event representationagainst the transport service representation to provide a visualpresentation of the network event affecting the transport service interms of the affected physical network elements, network entities, andconnections. The provided visual presentation enables a viewer tocorrelate in a visual manner the network event affecting the transportservice with the transport service affected by the network event.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing will be apparent from the following more particulardescription of example embodiments of the invention, as illustrated inthe accompanying drawings in which like reference characters refer tothe same parts throughout the different views. The drawings are notnecessarily to scale, emphasis instead being placed upon illustratingembodiments of the present invention.

FIG. 1A is a high level network diagram of a management network with atransport service supporting communications between points A and Z inthe network;

FIG. 1B is a high level network diagram of an example transport service,between points A and point Z, in the network which may be representedand visually presented by embodiments of the present invention;

FIG. 2 is a block diagram of a transport service display in which anembodiment of the present invention is employed;

FIGS. 3A-3C are partial transport service displays of network elements,network entities, and connections in which an embodiment of the presentinvention is employed;

FIG. 4 is a flow diagram illustrating an example process for displayinggraphical representations of a transport service according to anembodiment of the present invention;

FIG. 5 is a block diagram illustrating an example network manager inaccordance with an embodiment of the present invention;

FIG. 6A is a block diagram of a management unit process data of networkcomponents to create multiple graphical representations according toembodiments of the present invention;

FIG. 6B is a block diagrams of a network manager synchronizinginformation by employing an embodiment of the present invention;

FIGS. 7A-C are block diagrams and example screenshots of example networkevent representations, in accordance with embodiments of the presentinvention;

FIG. 8A is block diagram of an example visual presentation, inaccordance with an embodiment of the present invention;

FIGS. 8B and 8C are block diagrams comparing troubleshooting andanalyzing with an example visual presentation, in accordance with anembodiment of the present invention, and a typical presentation;

FIGS. 9A and 9B are flow diagrams of example processes for correlatingin a visual manner a network event affecting a transport service withthe transport service affected by the network event, in accordance withembodiments of the present invention;

FIGS. 10A-C are block diagrams of an example apparatus to correlate in avisual manner a network event affecting a transport service with thetransport service affected by the network event, in accordance withembodiments of the present invention; and

FIG. 11 is a block diagram of an example visual presentation withmaintained correlation states of each transport service supportingelement, in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

A description of example embodiments of the invention follows.

Today's network applications, such as third generation cellular (3G),have very diverse and complex mechanisms for providing transportservices. In particular, after a transport service (e.g., a 3G voicecall or data session) leaves a source (point A in a network) in onetechnology, the transport service is often contained and adapted (e.g.,encapsulated, multiplexed, and de-multiplexed) by different or relatedtechnologies several times before finally arriving at a target (point Zin the network).

Common techniques for displaying graphical representations of networkssummarize a network by representing the network at high level views,typically as physical network elements. In contrast, example embodimentsof the present invention illustrated in FIGS. 2-6B simultaneouslydisplay graphical representations for a transport service within anetwork by displaying network elements and connections between networkentities to form graphical representations, where the graphicalrepresentations show intra-element connections, inter-elementconnections, and relationships between the network entities to display atransport service from point A to point Z in the network. Thus, a usercan visualize a transport service and identify faults in the transportservice efficiently and on a substantially real-time basis.

A fault or a network event affecting the transport service may occur atvarious elements supporting the transport service, such as physicalnetwork elements, network entities within the physical network elements,and connections between the network entities. Consequently,troubleshooting and analyzing a network event affecting a transportservice may be aided by a correlation technique to correlate the networkevent affecting the transport service with the transport serviceaffected by the network event. In particular, to be effective, thecorrelation technique more than merely suppresses downstream alarms andindirect alarms on related transport service supporting elements.

Suppressing alarms attempts to isolate a root cause of a network faultand typically involves complex network information models and codinglogic to reduce many alarms into a single root cause alarm. However,despite reducing the number of alarms, a user is still required to“drill down” and investigate to identify a subject transport servicesupporting element. As such, additional steps are undertaken beforetroubleshooting and resolving the network faults can begin.

In contrast, example embodiments of the present invention illustrated inFIGS. 7-11 simultaneously presents a network event representationagainst the graphical representations for the transport service withinthe network (i.e., transport service representation) to provide a visualpresentation of the network event affecting the transport service interms of the affected physical network elements, network entities, andconnections. The provided visual presentation enables a viewer tovisually correlate the network event affecting the transport servicewith the transport service affected by the network event directly.

FIG. 1A is a high level network diagram 100 of a management network 130communicating from a point A to a point Z through use of a transportservice. The network diagram 100 includes a computer 105, configurationdata 110, Local Area Network (LAN) 115, network manager 120,configuration requests 125, network elements 135, point A 132, point Z137, configuration responses 140, graphical representation 145, trafficservice graphical representation 150, Element Management System (EMS)155, Optical Line Terminals(s) (OLTs) 160, Optical Network Terminal(s)(ONTs) 165, and end user devices 170.

In operation, a computer 105, such as a configuration computer, sendsthe configuration data 110 over the LAN 115 to the network manager 120.After receiving the configuration 110, the network manager 120 sends aconfiguration request 125 via the management network 130 to a firstnetwork element 135-1. In response, the first network element-1 135sends a configuration response 140 via the management network 130 to thenetwork manager 120. The configuration response 140 includes a state(e.g., operational or fault) for each network component supporting atransport service (e.g., network elements, network entities, andphysical and logical connections) and a relationship or baseline foreach network component. In an alternative embodiment, the networkmanager 120 may include a storage unit (e.g., a database) or a storageunit may be located outside the network manager. The storage unit storesstate and relationship information for each component.

It is useful to note that the network manager 120 may perform aconfiguration request 125 for each network component in a transportservice (e.g., the first network element 135-1 and a second networkelement 135-2). It should also be understood that the network manager120 can also send configuration requests 125 over multiple networklayers or multiple transport services. Further, the network manager 120may also communicate and manage one or more Element Management Systems(EMSS) 155, where the EMS 155 supports OLTs 160, ONTs 165, and possiblyend user devices 170.

After obtaining the state of each network component, the network manager120 generates a graphical representations 145, including a graphicalrepresentation of network components and corresponding states (e.g.,operational or fault). Next, the network manager 120 sends the graphicalrepresentations 145 to a Traffic Service Graphical Representation (TSGR)display 150. The TSGR 150 then displays the graphical representation 145to a user (e.g., a craft person display) with network elements, entitiesand connections in a manner that is simultaneous or in substantiallyreal-time, as described in detail blow beginning in reference to FIG. 2.It is useful to note that the graphical representations 145 mayhighlight or otherwise indicate a failure in a visual or auditorymanner.

In FIG. 1B, an example transport service components 150 that enablestraffic between a node B 155 and a Radio Network Controller (RNC) 160 ina Universal Mobile Telecommunications System (UMTS) Radio Access Network(UTRAN). More specifically, traffic is enabled between an interface onnode B 155 (i.e., point A 156) and an interface on the RNC 160 (i.e.,point Z 161). The transport service 150 between point A 156 and point Z161 is supported by a cell site aggregator 165, backhaul 170, andintegrated mobile group 175, which includes a switch 180 and a router185. Described below in reference to FIG. 2, the transport servicesupporting elements 165, 170, 175, 180, and 185, include networkelements, network entities within the network elements, and connectionsbetween the network entities.

The example transport service 150 is but one example and is used solelyfor purposes of illustrating and describing embodiments of the presentinvention with respect to the example. While the example transportservice 150 and other examples in this disclosure illustrated certainembodiments of the present invention with respect to third generation(3G) wireless, in no way are embodiments of the present inventionlimited to 3G wireless. One of ordinary skill in the art will readilyrecognize that principles of the present invention (to be furtherdescribed below) are applicable to other telecommunications networks,such as Global System for Mobile Communications (GSM), General PacketRadio Service (GPRS), Code Division Multiple Access 2000 (CDMA2000), andthe like. Future telecommunication networks, such as fourth generation(4G) wireless, are also within the contemplation of embodiments of thepresent invention.

Additionally, the principles of the present invention are alsoapplicable to related technologies, such as Pseudowire overMultiprotocol Label Switching (MPLS). Pseudowire over MPLS is a buildingblock upon which multiple types of traffic can be layered and thenconverged onto a single, multipurpose packet-switched network. Forexample, pseudowires may carry Time Division Multiplexing (TDM),Ethernet, Frame Relay, Asynchronous Transfer Mode (ATM) and High-LevelData Link Control/Point-to-Point Protocol (HDLC/PPP) traffic.

Moreover, these principles are equally applicable to computer networksand related technologies, such as (Asynchronous Transfer Mode (ATM)Passive Optical Network APON), Broadband Passive Optical Network (BPON),Gigibit Passive Optical Network (GPON), and the like.

FIG. 2 is a block diagram 200 of a transport service display 200 inwhich an embodiment of the present invention is employed. The transportservice display 200 provides a Graphics User Interface (GUI) thatincludes a graphical representation of network components (e.g., networkelements, network entities, and connections) for a transport service.More specifically, the transport service display 200 includes a point A210 communicating with a point Z 240, network layers 215, networkelements 220-1 . . . 4, network entities 225, connections 230, andadaptions 235. In a convenient embodiment, the transport service display200 allows a user to visually understand the transport service beingdisplayed and quickly identify a fault in a transport service byhighlighting a network component with faults, such as loss of signal(LOS) or high Bits Error Rate (BER). Further, the transport servicedisplay 20 also may provide access to network component, networkmanager(s), configuration information, state information, and alarmstatus for network components. The configuration information may besynchronized, as described below in reference to FIG. 6, with the eachnetwork component and maintained on a real-time basis.

In operation, a system employing embodiments of the present inventiondisplays data transmissions within a transport service from point A 210to point Z 240 over one or more network layers 215 and or one or morenetwork components (e.g., network elements, network entities, orconnections, which in some network systems, the network elements,entities and connecting may be referred to as shelves, cards, ports,logical entities, terminations, cross-connections or other typicalnetwork terms.

The transport service display 200 of FIG. 2 shows data transmissionbetween points A and Z over an intra-element link 250. An intra-elementlink 250 includes multiple network entities 225 in the same networklayer 215 and network element 220, as well as corresponding connections230 a-b. In example embodiments, a connection may include vertical andhorizontal connections. The vertical connections are sometimes referredto as adaptions because an adaption between two communications protocolsoccurs as data moves vertically between network layers. It should beunderstood that adaptions may sometimes be referred to as adaptations.Similarly, the vertical connections may also be referred to as acontainment because a containment between multiple protocols occur asdata moves vertically between network layers (e.g., a T3 that contains aT2). In the present example, the network entities 225 are connected viaphysical connecting 230 a or logical connections 230 b, where theconnections 230 carry a payload between the network entities 225.

Another example transport service display 205 is an inter-element link.An inter-element link includes multiple network entities 225 on the samenetwork layer 215 over separate network elements 220 1 . . . 4 (e.g.,network element 1 and network element 2). The network elements 220 1 . .. 4 may be connected via a physical media (e.g., wires, cables, orfiber) allowing the connection payload to transmit between the networkentities 225 over the physical media. Further, the transport servicedisplay 205 may also show one or more adaptions 235.

The adaption 235 representation may include a network entity 225 at onenetwork layer 215 a adapted to communicate with a network entity 225 ata different network layer 215 b in the same network element 230. Forexample, in FIG. 2, an ATM 250 communicates via adaption 235 to DigitalSignal 1 (DS1 260) over an Inverse Multiplexing for ATM (IMA) 255. Inuse, the IMA 255 expands ATM bandwidth of a Wide Area Network (WAN) fromT1 speeds by way of the represented adaption 235.

A transport service is shown in the transport service display of FIG. 2enabling traffic between a point A 210 and a point Z 240. The transportservice between point A 210 and point Z 240 is supported by networkelements 220-1 . . . 4, network entities 225 within the networkelements, and physical or logical connections 230 between the networkentities. In use, the transport service transmits data from point A 210through a network entity 226 a over a physical connection 230(represented by a solid black line) to a destination network entity 250.After receiving the data, the destination network entity 250 sends thedata to an ATM 226 b over a logical connection 230 (represented by adashed line). The data continues over each network entity and elementvia physical and logical connections unit arriving at point Z 240.

FIGS. 3A-3C are simplified partial transport service displays of anetwork elements, network entities, and connections according to anexample embodiment of the present invention.

FIG. 3A is a simplified partial transport service display 300 of anetwork element 305 (e.g., a Wide Area Network (WAN)) that includes apoint A 315 in a network entity 310 (e.g., Asynchronous Transfer Mode(ATM)) having a vertical connection 322 (e.g., adaption or containment)to a point Z 320. The transport service display 300 shows a faultindicator 325 on the vertical connection 322 representing a failure inthe vertical connection between the point A 315 and the point Z 320.More specifically, the transport service display 300 shows a faultindicator 325 when a connection between a point in an ATM and a point aWAN has a fault. By displaying the fault indicator 325, a user canquickly identify a problem in a vertical connection or other networkcomponent in a transport service display 300.

FIG. 3B shows a simplified partial transport service display 328 of afailure in a physical or logical horizontal connection 342 betweennetwork entity 1 335 (e.g., ATM 1) and a network entity 2 350 (e.g., ATM2). The transport service display 328 shows a fault indicator 345 in thehorizontal connection 342 representing a horizontal connection failurebetween a point A 340 and a point Z 355 across network entities (335,350). For example, the transport service display 328 shows a faultindicator 345 when a logical or physical horizontal connection between apoint in a first ATM and a second ATM fails.

FIG. 3C is a simplified partial transport service display 357 of afailure in a physical or logical horizontal connection 372 between anetwork element 1 360 (e.g., WAN 1) and a network element 2 380 (e.g.,WAN 2). A transport service display shows a fault indicator 375 on thehorizontal connection 372 representing a horizontal connection failurebetween the network elements (360, 380). By viewing the display, itshould be apparent that the failure occurs during a horizontalconnection between a point A 370 in a network entity 1 365 and a point Z390 in a network entity 2 385. More specifically, the transport servicedisplay 357 shows a fault indicator 375 for the horizontal connectionbetween point A 370 and point Z 390 allowing a user to view a graphicalrepresentation of a horizontal connection problem between two WANs(e.g., the network elements (360,380)). It should be understood that thefault indicator can include annotated text or graphical information atthe graphical representations. Further the transport service display 357may also add color, remove color, create shading, remove shading,provide an audio indication, or provide other suitable representationsto a user.

FIG. 4 is a flow diagram 400 illustrating an example process fordisplaying graphical representations of a transport service according toan embodiment of the present invention. After beginning, the exampleprocess creates (405) graphical representations for a transport service.After creating the graphical representations, the example processdisplays (410) the graphical representations to a user, computer, orsuitable output device for viewing.

FIG. 5 is a block diagram 500 illustrating an example network manager inaccordance with an embodiment of the present invention. In particular,FIG. 5 shows a network manager 505 that identifies failures for one ormore network component. The network manager 505 includes a managementunit 510, a craft person interface 515, a network components interface545, a storage unit 525, and a display unit 535. In this exampleembodiment, the management unit 510 manages network elements, physicalnetwork connections, network entities, vertical connections, andhorizontal connections in a Graphics User Interface (GUI) to identifyand graphically represent one or more failures.

In use, the management unit 510 makes a baseline request 520 to thestorage unit 525 and receives the baseline information 522 that includesrelationships for each network component in a transport service. Forexample, the management unit 510 receives a baseline (e.g., arelationship) for each network component. After obtaining baselineinformation, the management unit 510 compares the current relationshipwith a previous relationship. For example, if a baseline shows adifference between a previous network configuration, a graphicalrepresentation is created showing the change. That is, each differencerepresents a change in network conditions (e.g., a failure).

After identifying a change in the network conditions, the managementunit 510 sends each network condition 530 to a display unit 535. Thedisplay unit 535 creates a display 540 and sends the display 540 to auser. The display 540 graphically represents each network component andprovides highlights for each network component with change in networkconditions (e.g., a failure). It is useful to note that by highlightingthe network variations in each network component, a user can quicklyview the display and troubleshoot the network in a substantiallyreal-time manner. It should be understood that the display can includeone or more transport services and corresponding supporting networkcomponents. Viewing one or more transport services allows a user tosimultaneously identify failures in network traffic between a point Aand a point Z over one or more transport services.

FIG. 6A is a block diagram of a management unit 603 process data ofnetwork components to create multiple graphical representationsaccording to embodiments of the present invention. In particular, FIG.6A shows a management unit 603 that includes a graphical representationsmodule 630, a display control module 640, and a display 652. In thisexample embodiment, the graphical representations module 630 of themanagement unit 603 receives data from one or more network components ina transport service 623. After receiving the data, the graphicalrepresentations module 630 generates a graphical representation 632 andsends the graphical representation 632 for each network component to thedisplay control module 640. The display control module 640 processes thegraphical representation 632 for each network component in the transportservice and sends multiple graphical representations 642 (e.g., of eachnetwork component) to the display 652. The display 652 allows a user toview graphical representations for each network component in thetransport service.

FIG. 6B is a block diagram 600 of a management unit 605 synchronizinginformation by employing an embodiment of the present invention. Inparticular, FIG. 6B shows a management unit 605 that includes aTransport Service Communications Module (TSCM) 610 (e.g., synchronizer),a graphical representations module 630, a display control module 640, astatus manager 650, a baseline manager 660, and a configuration manager670. In this example embodiment, the management unit 605 interacts witheach network module or manager to synchronize data or information.

In use, the management unit 605 makes a component information request615 to one or more network devices. The network devices reply with acomponent information response 620 for each network device. In turn, theTSCM 610 separates the component information response 620 into statusinformation 645, baseline information 655, and configuration information665. The TSCM 610 synchronizes the status information 645 with thestatus manager 650, the baseline information 655 with the baselinemanager 660, and configuration information 665 with the configurationmanager 670. Once the information is synchronized, the TSCM 610 sendsthe display information 635 to display control module 640 and GUIinformation 625 to the graphical representations module 630.

After receiving the GUI information 625, the graphical representationsmodule 630 sends one or more graphical representations 632 to the TSCM610. Likewise, after receiving the display information 635, the displaycontrol module 640 creates a updated display information 642, includingone or more graphical representations, and returns the updated displayinformation 642 to the TSCM 610. Next, the TSCM 610 sends (670) theupdated display information including each graphical representation to acomputer or user. It should be understood that the TSCM 610 is used forillustrative purposes only and the modules and managers may be placed incentral modules or managers. It should be also be understood that themanagement unit 605 can add or remove modules and managers asappropriate.

In view of the foregoing, it should be understood that many embodimentsof the present invention are possible. For example, a method orcorresponding apparatus in an example embodiment of the presentinvention graphically represents physical network elements, networkentities within the physical network elements, and connections (e.g.,physical and logical connections) between the network entities to formgraphical representations. Next, a method employing the embodimentsimultaneously displays the graphical representations in a mannershowing intra-element connections, inter-element connections, andrelationships between the network entities to display a transportservice from point A to point Z in the network. Further, the graphicalrepresentations can be provided to a user in a single display interface.

In an example embodiment, displaying the status of the transport serviceincludes identifying a fault in the transport service based oninformation received from the physical network elements, networkentities, or a network node associated with the transport service.

In yet another embodiment of the present invention, an exampleembodiment stores a baseline of the transport service, determines apresent state of the transport service, and highlights a differencebetween the baseline and present states in a simultaneously display. Forconvenience, the highlighting may include at least a subset of thegraphical representations. For further convenience, the highlighting mayinclude presenting annotating text or graphical information at thegraphical representations, adding color, removing color, creatingshading and removing shading.

In still another embodiment of the present invention, an exampleembodiment the displaying a status of the transport service may beperformed in a substantially real-time basis.

In still yet another embodiment of the present invention, an exampleembodiment manages the physical network connections, network entities,and connections through Graphical User Interface (GUI) interaction withthe graphical representations. Further, a display may be selectivelydisplaying expanded and collapsed parallel connections in transportservice. For example, the display can show multiple transport services(e.g., expanded parallel connections) or a single transport service(collapsed parallel connections).

It should be understood that any of the processes disclosed herein, suchas the graphical representations or the flow diagrams of FIG. 4, may beimplemented in the form of hardware, firmware, or software. Ifimplemented in software, the software may be processor instructions inany suitable software language and stored on any form of computerreadable medium. The processor instructions are loaded and executed by aprocessor, such as a general purpose or application specific processorthat, in turn, performs the example embodiments disclosed herein.

As describe above in reference to FIGS. 2-6, example embodiments of thepresent invention simultaneously display graphical representations for atransport service within a network by displaying network elements andconnections between network entities to form graphical representations,where the graphical representations show intra-element connections,inter-element connections, and relationships between the networkentities to display a transport service from point A to point Z in thenetwork. In this way a user can visualize a transport service andidentify faults in the transport service efficiently and on asubstantially real-time basis.

Now described below in reference FIGS. 7-11, example embodiments of thepresent invention simultaneously present a network event representationagainst a transport service representation (e.g., a graphicalrepresentation of transport service within a network) to provide avisual presentation of the network event affecting the transport servicein terms of the affected physical network elements, network entities,and connections.

In FIG. 7A, an example transport service representation 700 represents atransport service 705 between a point A 706 and a point Z 707 in termsof a first transport service supporting element through an nth transportservice supporting element (710 a . . . 710 n, generally 710 a-n). Asdescribed in reference to FIG. 2, the transport service supportingelements 710 a-n includes network elements (e.g., the network elements220), entities (e.g., the entities 225), and connections (e.g., theconnections 230).

In the example illustrated in FIG. 7A, one embodiment collects from aportion of the transport service supporting elements 710 a-n, statusinformation 715 a and 715 b. The collected status information 715 a, 715b indicates network event(s) affecting transport service. Based on thecollected information 715 a, 715 b a representation 720 represents thenetwork event(s) affecting transport service.

The collected status information 715 a, 715 b may be actively collected,for example, using a request message to request for the statusinformation 715 a, 715 b and a response message to respond with thestatus information 715 a, 715 b. Alternatively, the collected statusinformation 715 a, 715 b may be passively collected, for example, anupdate message may provide the status information 715 a, 715 bperiodically or resulting from a triggering event. However, one ofordinary skill in the art will readily recognize the act of collectingthe status information 715 a, 715 b to form the network eventrepresentation 720 is of greater significance than whether a mechanismfor collecting the status information 715 a, 715 b is active or passive.As such, despite a possible inference of embodiments of the presentinvention collecting status information actively, principles of thepresent invention are not intended to be limited by such an inference.

In FIG. 7B, an alternative embodiment collects from a subject transportservice supporting element 735 and related transport service supportingelements 740, state information (745 and 750, respectively). Thecollected status information 745 and 750 indicate of a network eventaffecting both the subject and the related transport service supportingelements 735 and 740.

A transport service representation 730 represents an example transportservice between a point A 731 and a point Z 732 in a network. Thetransport service representation 730 organizes the subject transportservice supporting element 735 and the related transport servicesupporting elements 740 into a same network level 741. The relatedtransport service supporting elements 740 are denoted in FIG. 7C, asdescribed in detail below, by a dotted and dashed outline 780.

A relationship exists between transport service supporting elements at asame network level (i.e., transport service supporting elements on asame network level are related). Transport service supporting elementsmay also be related on different network levels (e.g., one network layerabove or below another network layer).

Because a relationship exists between a subject supporting element andrelated transport service supporting elements, often a network eventdirectly affecting the subject transport service supporting element alsoaffects the related transport service supporting elements indirectly(i.e., the network event has an indirect effect). As such, statusinformation collected from related transport service supporting elementsmay be useful for correlating a network event affecting a transportservice with the transport service affected by the network event. Inthis way the aforementioned embodiment does not, or may at controlledlevels, suppress indirect indications from related transport servicesupporting elements which indicate a network event affecting transportservice.

Continuing to refer to FIG. 7B, based on the collected statusinformation 745 and 750, a representation 755 represents the networkevent affecting both the subject transport service supporting element735 and the related transport service elements 740.

FIG. 7C is a screen shot illustrating an alternative embodiment thatcollects, from a subject transport service supporting element 775 anddownstream supporting elements 780, status information 785 and 790,respectively. The collected status information 785 and 790 indicate anetwork event affecting both the subject and the downstream supportingelements 775 and 780, respectively.

A transport service representation 760 represents an example transportservice between a point A 761 and a point Z 762 traversing the subjectsupporting element 775 and the downstream supporting elements 780. Thedownstream supporting elements 780 are denoted in FIG. 7C by a dottedand dashed outline 780.

A network event affecting a subject transport service supporting elementoften affects the transport service downstream supporting elements(i.e., the network event has a downstream effect). As such, statusinformation collected from downstream supporting elements may be usefulfor correlating a network event affecting a transport service with thetransport service affected by the network event. In this way theaforementioned embodiment does not suppress downstream, indications fromdownstream transport service supporting elements which indicate anetwork event affecting transport service.

Continuing to refer to FIG. 7C, based on the collected statusinformation 785 and 790, a representation 795 represents the networkevent affecting both the subject transport service supporting element775 and the transport service downstream elements 780.

The embodiments illustrated in and described in reference to FIGS. 7A-Care contrasted with reducing a number of indications or alarms asgenerally done in the prior art. In prior art systems involving reducingthe number of alarms (often to a single alarm), invariably requirecomplex network information modeling and coding logic to achieve alarmreduction. However, even with the number of alarms reduced, a user, suchas a network administrator, is still required to spend time and “drilldown” to identify the correct transport service supporting element tobegin troubleshooting and resolving a network fault. Reducing the numberof alarms presented to the user, for example, by suppressing alarms fromrelated or downstream supporting elements does not necessarily result inless time spent troubleshooting or resolving a network event affectingtransport service.

Here, to troubleshoot and analyze a network event, at least some exampleembodiments, contrary to simply presenting fewer alarms, present ahighly structured and comprehensive visual presentation depicting anetwork event affecting a transport service in terms of the transportservice supporting elements affected by the network event. Even inembodiments (described in reference to FIG. 11) which may “reduce” thenumber of alarms presented, such embodiments still provide a highlystructured and comprehensive visual presentation. In either instance,the provided visual presentation enables a viewer to correlate in avisual manner the network event affecting the transport service with thetransport service affected by the network event directly.

To illustrate, consider a comparison between troubleshooting andanalyzing a network event affecting a transport service between twopoints in a network using a visual presentation according to embodimentsof the present invention illustrated in FIG. 8B and a typicalpresentation illustrated in FIG. 8C. But before the comparison, consideran example illustrated in FIG. 8A generally applying principles of thepresent invention.

In FIG. 8A, an example transport service representation 800 represents atransport service 805 between a point A 806 and a point Z 807 in termsof a first transport service supporting element through an nth transportservice supporting element (810 a . . . 810 n, generally 810 a-n). Asdescribed in reference to FIG. 2, the transport service supportingelements 810 a-n includes network elements (e.g., the network elements220), entities (e.g., the network entities 225), and connections (e.g.,the connections 230).

Also in FIG. 8A, a network event representation 815 represents a networkevent affecting the transport service 805.

A visual presentation 825 simultaneously presents the network eventrepresentation 815 against the transport service representation 800.Because the transport service representation 800 represents thetransport service 805 in terms of transport service supporting elements810 a-n while the network event representation 815 represents thenetwork event affecting the transport service 805, simultaneouslypresenting the representations 800 and 815, one against another, theresulting visual presentation 820 presents the network event affectingthe transport service 805 in terms of the affected transport servicesupporting elements 810 a-n (namely, the affected physical networkelements, network entities, and connections). The provided visualpresentation 820 enables a viewer to correlate visually the networkevent, affecting the transport service 805, with the transport service805, affected by the network event.

Additionally, in the example embodiment illustrated in FIG. 8A,indicator boxes 825 a and 825 b, generally 825 indicate the networkevent affecting the first and third transport service supportingelements 810 a and 810 c. The indicator boxes 825 provide a visual cueof the transport service affected by the network event. One of ordinaryskill in the art will readily recognize that the indicator box 825 maytake any form or format, such as highlights, flashing graphics, colorchanges, or other visual cues.

However, contrary to the indicator boxes 825, it is useful to note thatthe first and third transport service supporting elements 810 a and 810c are not necessarily both affected by the network event directly. Inone case, the first transport service supporting element 810 a-na may beaffected by the network event directly (i.e., a subject transportservice supporting element) and the third supporting element 810 c maybe affected by the network event indirectly, or vice versa.

In such cases, the embodiment illustrated in FIG. 8A indicates at leasta portion of the transport service supporting elements 810 a-n affectedby the network event, thereby providing a visual cue of the networkevent affecting the portion of the transport service supporting elements810 a-n. In this way a viewer sees the network event affecting thetransport service in terms of the affected portion of the transportservice supporting elements as contrasted with, in this exampleembodiment, seeing only a reduced number of alarms. Consequently, theviewer is able to correlate visually the network event affecting thetransport service, with the transport service affected by the networkevent.

An alternative embodiment (not shown) indicates a subject transportservice supporting element and transport service supporting elementsrelated to the subject transport service supporting element affected bythe network event. By doing so, the embodiment provides a visual cue ofthe network event affecting both the subject and the related transportservice supporting elements. In this way, a viewer sees the networkevent affecting the transport service in terms of the affected subjectand related transport service supporting elements as contrasted with, inthis example embodiment, seeing only a reduced number of alarms.

Another alternative embodiment (not shown) indicates a subject transportservice supporting element and transport service supporting elementsdownstream of the subject transport service supporting element affectedby a network event. By doing so, the embodiment provides a visual cue ofthe network event affecting both the subject and the downstreamtransport service supporting elements. In this way a viewer sees thenetwork event affecting the transport service in terms of the affectedsubject and downstream transport service supporting elements ascontrasted with, in this example embodiment, seeing only a reducednumber of alarms.

FIG. 8B is a visual presentation 830 that visually presents a transportservice 835 between a point B 836 and a point C 837 in terms of elements840, 845 and 847 supporting the transport service 835. Included are afirst network element 840 a and a second network element 840 b (e.g.,TELLABS 5500 TRANSPORT SWITCH and TELLABS 8860 MULTI-SERVICE ROUTER).The first network element 840 a includes, among other things, a T1network entity 845 a, a T3 network entity 845 b, and an OC3 networkentity 845 c, generally 845.

The network entities 845 are connected by vertical connections 847 a andhorizontal connections 847 b. The vertical connections 847 a representadaptions from one network entity into another (e.g., from the T1 entity845 a into the T3 entity 845 b). In illustrated example, the T1 entity845 a is multiplexed (or otherwise adapted) with other T1 entities (notshown) into the T3 entity 845 b. The T3 entity 845 b is furthermultiplexed with other T3 entities (not shown) into the OC3 entity 845c.

The horizontal connectors 847 b represent “logical links” (e.g., alogical link 847 b-1) and “physical links” (e.g., a physical link 847b-2) between “peer” network entities. The physical link 847 b-2 connectspeer entities with a physical media. In the illustrated example, thephysical link 847 b-2 represents a fiber optic connection between peerentities. The physical link 847 b-2 is not limited to fiber, but mayconnect peer entities with, for example, copper, wireless or otherphysical media.

The logical link 847 b-1 connects peer entities, not physically, butlogically. For example, a first peer originates a communication (e.g.,data, signaling, etc.) per a protocol and a second peer terminates thecommunication per the protocol. Because the first and second peerscommunicate to each per the protocol, there is a logical connection(i.e. relationship) between the first and second peers, which isrepresented by the logical link 847 b-1.

The second network element 840 b includes T1, T3, OC3 network entities845 d-f, which are connected to one another by the vertical connections847 a and horizontal connections 847 b. The logical link 847 b-1logically connects the T1 entities 845 a and 845 d. The physical link847 b-2 physically connects the OC3 entities 845 c and 845 f.

In the example illustrated in FIG. 8B, the logical link 847 b-1 betweenthe T1 entities 845 a and 845 d is set-off visually by an indicator box849. The indicator box indicates that the logical link 847 b-1 isaffected by the network event. In this way the visual presentation 830visually presents the network event affecting the transport service 835between the point B 836 and the point C 837 in terms of the logical link847 b-1 between the T1 entities 845 a and 845 d affected by the networkevent.

In FIG. 8C, a typical presentation 850 presents a network eventaffecting a transport service 855 between a point B 856 and a point C857 in terms of a first network element 860 a and a second networkelement 860 b being affected by the network event. An indication box 875a indicates the network event affecting the first network element 860 a.Recall, however, a network element includes network entities within thenetwork element and connections between the network entities. As such,it is not clear from the indication box 875 a whether the first networkelement 860 a or the network entities within the first network element860 a are affected by the network event. Further troubleshooting andanalysis is supported by allowing an operator to expand the presentation850 into a first expanded presentation 851 a.

The first expanded presentation 851 a presents an OC3 entity 865 aaffected by the network event. An indication box 875 b indicates thenetwork event affecting the OC3 entity 865 a. However, as describedpreviously, there is a connection (adaption between an OC3 entity and aT3 entity, namely, multiple T3 entities (specifically three) aremultiplexed to a single OC3 entity. As such, it is not clear from theindication box 875 b whether the OC3 entity 865 a or one of themultiplexed T3 entities is affected by the network event. Accordingly,further troubleshooting and analysis is supported by enabling expandingthe first expanded presentation 851 a into a second expandedpresentation 851 b.

The second expanded presentation 851 b expands the OC3 entity 865 a intoa first, second, and third T3 entities 865 b-1, 2, and 3 (generally 865b) because an OC3 entity multiplexes three T3 entities. Moreover, thesecond expanded presentation 851 b presents one of three T3 entities 865b affected by the network event. An indication box 875 c indicates thenetwork event affecting the second T3 entity 865 b-2. However, becausethere is a connection (adaption) between a T3 entity and a T1 entity,namely, multiple T1 s (specifically 28), are multiplexed into a singleT3 entity, it is not clear from the indication box 875 c whether thenetwork event affects the second T3 entity 865 b-2 or a T1 entitymultiplexed by the second T3 entity 865 b-2. Accordingly, furthertroubleshooting and analysis is supported by enabling expanding thesecond expanded presentation 851 b into a third expanded presentation851 c.

The third expanded presentation 851 c expands the second T3 entity 865b-2 into a first through twenty-eighth T1 entities 865 c-1 . . . 28(generally 865 c) because a T3 entity multiplexes twenty-eight T1entities. Moreover, the third expanded presentation 851 c presents oneof the twenty eight T1 entities 865 c as being affected by the networkevent. An indication box 875 d indicates the network event affecting thethird T1 entity 865 c-3.

However, because there is a connection (logical link) between T1 peerentities, it is not clear from the indication box 875 d whether thenetwork event affects the third T1 entity 865 c-3 or a connectionbetween it and its peer. Accordingly, further troubleshooting andanalysis is supported by enabling expanding the third expandedpresentation 851 c into a fourth expanded presentation 851 d.

The fourth expanded presentation 851 d expands the third T1 entity 865c-3 into a connection 870 between the third T1 entity 865 c-3 and itspeer. Moreover, the fourth expanded presentation 851 d presents theconnection 870 as being affected by the network event. An indication box875 e indicates the network event affecting the connection 870.

As illustrated, presenting the network event affecting the transportservice 855 in terms of the connection 870 between the third T1 entity865 c-3 and its peer requires a series of presentation and expandedpresentations 850 and 851 a-d. A similar series of presentation andexpanded presentations may be required beginning with a presentation ofthe network event affecting the second network element 860 b.

Each presentation (850 and 851 a-d) enables an operator to expand orotherwise “drill down” from a previous presentation. Consequently,additional steps (and time) are required for troubleshooting andanalyzing a network event affecting a transport service.

Even if a presentation were to present, using complex information modelsand coding logic, a reduced number of transport service supportingelements affected by a network event, such a presentation still requiresexpanding. Each presentation presents the network event affecting atransport service in terms of a transport service supporting elementseparate and in isolation of other elements supporting the transportservice (e.g., downstream and related transport service supportingelements described in reference to FIGS. 7A-C). A network eventaffecting a connection between network entities may be presented in apresentation which presents a network event affecting a transportservice in terms of connection between entities, but not inpresentations which present the network event affecting the transportservice in terms of either the network element or the network entities.

In FIG. 9A, an example process 900 visually correlates a network eventaffecting a transport service with the transport service affected by thenetwork event. The process 900 starts (901) visually correlating anetwork event with a transport service. The transport service is betweena point A and a point Z in a network. The process 900 represents (905)the transport service in terms of physical network elements, networkentities within the physical network elements, and connections betweenthe network entities to form a representation of the transport service.The formed transport service representation shows connections within anetwork element (intra-network element connections), connections betweennetwork elements (inter-network element connections), and relationshipsbetween the network entities.

The process 900 represents (910) a network event affecting the transportservice to a form a representation of the network event.

The process 900 simultaneously presents (915) the network eventrepresentation against the transport service representation to provide apresentation of the network event affecting the transport service interms of the physical network elements, the network entities, and theconnections affected. The provided presentation enables a viewer tovisually correlate the network event, affecting the transport service,with the transport service, affected by the network event.

The process 900 ends (916) with the network event visually correlatedwith the transport service.

In FIG. 9B, another example process 950 visually correlates a networkevent affecting a transport service with the transport service affectedby the network event. The process 950 starts (951) visually correlatinga network event with a transport service. The transport service isbetween a point A and a point Z in a network. The process 950 represents(955) the transport service in terms of physical network elements,network entities within the physical network elements, and connectionsbetween the network entities to form a representation of the transportservice. The formed representation shows connections within a networkelement (intra-network element connections), connections between networkelements (inter-network element connections), and relationships betweenthe network entities.

The process 950 collects (960) from at least a portion of the physicalnetwork elements, network entities, and connections (i.e., transportservice supporting elements), status information indicative of thenetwork event affecting the transport service. The collected informationrepresents the network event affecting the transport service.

In an alternative embodiment, the process 950 collects (not shown) froma subject transport service supporting element and transport servicesupporting elements related to the subject transport service supportingelement, status information indicative of a network event affecting boththe subject and the related transport service supporting elements. Assuch, the collected information represents the network event affectingthe transport service in terms of both the subject transport servicesupporting element and the related transport service supportingelements.

In another alternative embodiment, the process 950 collects (not shown)from a subject transport service supporting element and transportservice supporting elements downstream of the subject transport servicesupporting element, status information indicative of a network eventaffecting both the subject and the downstream transport servicesupporting elements. As such, the collected information represents thenetwork event affecting the transport service in terms of both thesubject transport service supporting element and the downstreamtransport service supporting elements.

Continuing with FIG. 9B, the process 950 indicates (965) at least aportion of the transport service supporting elements which are affectedby the network event. The indicated transport service supportingelements provides a visual cue of the transport service affected by thenetwork event.

In an alternative embodiment, the process 950 indicates (not shown) asubject transport service supporting element and transport servicesupporting elements related to the subject transport service supportingelement which are affected by the network event. As such, the indicatedsubject and related transport service supporting elements provide avisual cue of the transport service affected by the network event, interms of the subject and the related transport service supportingelements.

In another alternative embodiment, the process 950 indicates (not shown)a subject transport service supporting element and transport servicesupporting elements downstream of the subject transport servicesupporting element which are affected by the network event. As such, theindicated subject and downstream transport service supporting elementsprovide a visual cue of the transport service affected by the networkevent, in terms of the subject and the downstream transport servicesupporting elements.

The process 950 ends (966) with the network event visually correlatedwith the transport service.

In FIG. 10A, an example apparatus 1000 visually correlates a networkevent affecting a transport service with the transport service affectedby the network event. The apparatus 1000 includes a first representationunit 1005 to represent a transport service between point A and point Zin a network in terms of physical network elements, network entitieswithin the physical network elements, and connections between thenetwork entities and to form a representation of the transport service1006. The formed transport service representation 1006 showsintra-network element connections, inter-network element connections,and relationships between the network entities.

The apparatus 1000 also includes a second representation unit 1010 torepresent a network event affecting the transport service to form arepresentation of the network event 1011.

The apparatus 1000 further includes a presentation unit 1015 coupled tothe first representation unit 1005 and the second representation unit1010 to simultaneously present the network event representation 1011against the transport service representation 1006 to provide a visualpresentation 1016 of the network event affecting the transport servicein terms of the affected physical network elements, the networkentities, and the connections. The provided visual presentation 1016enables a viewer to visually correlate the network event affecting thetransport service, with the transport service affected by the networkevent.

Elements of the example apparatus 1000, namely, the first representationunit 1005, the second representation unit 1010, and the presentationunit 1015, may be co-located, as illustrated in FIG. 10A. For example,they may be co-located in the Status Manager 650 of FIG. 6.Alternatively, these elements may be distributed amongst the variousmanagers and modules described in reference to FIG. 6.

Whether co-located in a single entity or distributed amongst severalentities, in an embodiment illustrated in FIG. 10B, a secondrepresentation unit 1060 (e.g., the second representation unit 1010 ofFIG. 10A) includes a collection unit 1065 made to collect from at leasta portion of the transport service supporting elements, statusinformation 1066 indicative of the network event affecting the transportservice.

The second representation unit 1060 also includes a formation unit 1070coupled to the collection unit 1065 made to form, based on the collectedinformation 1066, a representation 1071 of the network event affectingthe transport service.

In an alternative embodiment (not shown), a collection unit is made tocollect from a subject transport service supporting element andtransport service supporting elements related to the subject transportservice supporting element, status information indicative of the networkevent affecting both the subject and the related transport servicesupporting elements.

In another alternative embodiment (not shown), a collection unit is madeto collect from a subject transport service supporting element andtransport service supporting elements downstream of the subjecttransport service supporting element, status information indicative ofthe network event affecting both the subject and the downstreamtransport service supporting elements.

Whether co-located in a single entity or distributed amongst severalentities, in an embodiment illustrated in FIG. 10C, a presentation unit1080 (e.g., the presentation unit 1015 of FIG. 10A) includes anindication unit 1085 made to indicate at least a portion of thetransport service supporting elements affected by the network event. Inparticular, the indication unit 1085 accepts (or otherwise process) atransport service representation 1086 and a network event representation1087.

The presentation unit 1080 also includes a visual cue unit 1090 coupledto the presentation unit 1080 made to provide a visual cue (orpresentation) 1095 of the network event affecting the transport servicein terms of the affected portion of the transport service supportingelements.

In an alternative embodiment (not shown), an indication unit is made toindicate a subject transport service supporting element and transportservice supporting elements related to the subject transport servicesupporting element affected by the network event. Additionally, in thisembodiment, a visual cue unit is made to provide a visual cue of thenetwork event affecting the transport service in terms of both theaffected subject and related transport service supporting elements.

In an alternative embodiment (not shown), an indication unit is made toindicate a subject transport service supporting element and transportservice supporting elements downstream of the subject transport servicesupporting element affected by the network event. Additionally, in thisembodiment, a visual cue unit is made to provide a visual cue of thenetwork event affecting the transport service in terms of both theaffected subject and downstream transport service supporting elements.

In FIG. 11, a visual presentation 1100 a visually presents, before anetwork event occurring, a transport service 1105 between a point A 1106and a point Z 1107 in terms of a first through an nth transport servicesupporting element 1110 a . . . 1110 n, generally 1110 a-n.

An embodiment illustrated in FIG. 11 maintains a correlation state foreach of the transport service supporting elements 1110 a-n. Themaintained correlation state indicates whether status information from atransport service supporting element is to be collected in an event anetwork event affects a transport service. Additionally, the maintainedcorrelation state indicates whether a network event affecting atransport service supporting element is to be indicated in an event thenetwork event affects the transport service.

The embodiment, based on the maintained correlation state for each ofthe transport service supporting elements 1110 a-n, provides acorrelation state indicator (a visual cue) 1115. In the illustratedexample, the correlation state indicators 1115 a-c indicate that for thetransport service supporting elements 1110 b, 1110 d and 1110 e, statusinformation is not collected and a network event affecting a transportservice supporting element is not indicated in an event the networkevent affects the transport service 1105.

Further in FIG. 11, a visual presentation 1100 b visually presents,after a network event occurring, the transport service 1105 in terms ofaffected transport service supporting elements 1110 c and 1110 f(indicated by network event indicators 1120 a and 1120 b) and thetransport service supporting elements 1110 b, 1110 d and 1110 e whosecorrelation states indicate that status information is not collected anda network event affecting a transport service supporting element is notindicated. In this way a viewer visually recognizes for which transportservice supporting elements, status information is not collected and anetwork event affecting a transport service supporting element is notindicated, in an event a network event affects transport service.

Because status information from the transport service supportingelements 1110 b, 1110 d and 1110 e are not collected nor is a networkevent affecting the transport service supporting elements 1110 b, 1110 dand 1110 e indicated, the network event affecting the transport service1105 may or may not be affecting the transport service supportingelements 1110 b, 1110 d and 1110 e. As such, the embodiment may reducethe number of alarms presented. However, in contrast to merelysuppressing alarms, the visual presentation 1100 b, through thecorrelation state indicators 1115, still enables a viewer to visuallycorrelate a network event affecting a transport service, with thetransport service affected by the network event without having to expanda previous presentation (described in reference to FIGS. 8B-C).

While this invention has been particularly shown and described withreferences to example embodiments thereof, it will be understood bythose skilled in the art that various changes in form and details may bemade therein without departing from the scope of the inventionencompassed by the appended claims.

It should be understood that the block and flow diagrams (e.g., FIGS.8A-C, FIGS. 9A-B, and FIGS. 10A-C) may include more or fewer elements,be arranged differently, or be represented differently. It should beunderstood that implementation may dictate the block/flow/networkdiagrams and the number of block and flow diagrams illustrating theexecution of embodiments of the invention.

It should be understood that elements of the block and flow diagrams(e.g., FIGS. 8A-C, FIGS. 9A-B, and FIGS. 10A-C) described above may beimplemented in software, hardware, or firmware. In addition, theelements of the block and flow diagrams described above may be combinedor divided in any manner in software, hardware, or firmware. Ifimplemented in software, the software may be written in any languagethat can support the embodiments disclosed herein. The software may bestored on any form of computer readable medium, such as random accessmemory (RAM), read only memory (ROM), compact disk read only memory(CD-ROM), and so forth. In operation, a general purpose or applicationspecific processor loads and executes the software in a manner wellunderstood in the art.

1. A method for correlating a network event affecting a transportservice with the transport service affected by the network event, themethod comprising: representing a transport service between point A andpoint Z in a network in terms of physical network elements, networkentities within the physical network elements, and connections betweenthe network entities to form a representation of the transport service,the formed transport service representation showing intra-networkelement connections, inter-network element connections, andrelationships between the network entities; representing a network eventaffecting the transport service to form a representation of the networkevent; and simultaneously presenting the network event representationagainst the transport service representation to provide a visualpresentation of the network event affecting the transport service interms of the affected physical network elements, network entities, andconnections, the provided visual presentation enabling a viewer tocorrelate in a visual manner the network event affecting the transportservice with the transport service affected by the network event.
 2. Themethod of claim 1 wherein the physical network elements, networkentities, and connections are transport service supporting elements, andwherein representing the network event includes: collecting, from atleast a portion of the transport service supporting elements, statusinformation indicative of the network event affecting the transportservice; and based on the collected information, representing thenetwork event affecting the transport service.
 3. The method of claim 2wherein collecting the status information includes collecting the statusinformation actively by requesting the status from the network elementsor entities or managers of the network elements or entities.
 4. Themethod of claim 2 wherein collecting the status information includescollecting, from a subject transport service supporting element andtransport service supporting elements related to the subject transportservice supporting element, status information indicative of the networkevent affecting both the subject supporting element and the supportingelements related to the subject supporting element.
 5. The method ofclaim 2 wherein collecting includes collecting, from a subject transportservice supporting element and transport service supporting elementsdownstream of the subject transport service supporting element, statusinformation indicative of the network event affecting both the subjectsupporting element and the supporting elements downstream of the subjectsupporting element.
 6. The method of claim 1 wherein the physicalnetwork elements, network entities, and connections are transportservice supporting elements and wherein simultaneously presenting thenetwork event representation against the transport servicerepresentation includes: indicating at least a portion of the transportservice supporting elements affected by the network event; and based onindicating, providing a visual cue of the network event affecting thetransport service in terms of the at least portion of the transportservice supporting elements affected by the network event.
 7. The methodof claim 6 wherein indicating the at least portion of the transportservice supporting element affected by the network event includes:indicating a subject transport service supporting element and transportservice supporting elements related to the subject transport servicesupporting element affected by the network event; and based on theindicating, providing a visual cue of the network event affecting thetransport service in terms of both the subject supporting element andthe supporting elements related to the subject supporting elementaffected by the network event.
 8. The method of claim 6 whereinindicating the at least portion of the transport service supportingelement affected by the network event includes: indicating a subjecttransport service supporting element and transport service supportingelements downstream of the subject transport service supporting elementaffected by the network event; and based on indicating, providing avisual cue of the network event affecting the transport service in termsof both the subject supporting element and the supporting elementsdownstream of the subject supporting element affected by the networkevent.
 9. The method of claim 1 wherein the physical network elements,network entities, and connections are transport service supportingelements, and wherein the method further comprises: maintaining acorrelation state of each transport service supporting element to definea maintained correlation state, the maintained correlation statesindicative of whether status information from respective transportservice supporting elements is to be collected and whether respectivetransport service supporting elements affected by the network event areto be indicated, in an event the network event affects the transportservice; based on the maintaining, providing a visual cue of thecorrelation state of each transport service supporting element to enablethe viewer to recognize visually for which transport service supportingelement in the visual presentation status information is not collectedand a network event affecting transport service supporting element isnot indicated, in an event the network event affects transport service.10. The method of claim 1 further comprising providing data tipsresponsive to interaction with at least one representation in graphicaluser interface manner.
 11. The method of claim 1 further comprisingannotating a tool tip responsive to interaction with at least onerepresentation in graphical user interface manner.
 12. An apparatus tocorrelate visually a network event affecting a transport service withthe transport service affected by the network event, the apparatuscomprising: a first representation unit to represent a transport servicebetween point A and point Z in a network in terms of physical networkelements, network entities within the physical network elements, andconnections between the network entities to form a representation of thetransport service, the formed transport service representation showingintra-network element connections, inter-network element connections,and relationships between the network entities; a second representationunit to represent a network event affecting the transport service toform representations of the network event; and a presentation unitcoupled to the first representation unit and the second representationunit to simultaneously present the network event representation againstthe transport service representation to provide a visual presentation ofthe network event affecting the transport service in terms of theaffected physical network elements, network entities, and connections,the provided visual presentation enabling a viewer to correlate in avisual manner the network event affecting the transport service with thetransport service affected by the network event.
 13. The apparatus ofclaim 12 wherein the physical network elements, network entities, andconnections are transport service supporting elements and wherein thesecond representation unit includes: a collection unit made to collectfrom at least a portion of the transport service supporting elements,status information indicative of the network event affecting thetransport service; and a formation unit coupled to the collection unitmade to form, based on the collected information, a representation ofthe network event affecting the transport service.
 14. The apparatus ofclaim 13 wherein the collection unit is made to collect from a subjecttransport service supporting element and transport service supportingelements related to the subject transport service supporting element,status information indicative of the network event affecting both thesubject supporting element and the supporting elements related to thesubject supporting element.
 15. The apparatus of claim 13 wherein thecollection unit is made to collect from a subject transport servicesupporting element and transport service supporting elements downstreamof the subject transport service supporting element, status informationindicative of the network event affecting both the subject supportingelement and the supporting elements downstream of the subject supportingelement.
 16. The apparatus of claim 12 wherein the physical networkelements, network entities, and connections are transport servicesupporting elements and wherein the presentation unit includes: anindication unit made to indicate at least a portion of the transportservice supporting elements affected by the network event; and a visualcue unit coupled to the indication unit made to provide a visual cue ofthe network event affecting the transport service in terms of the atleast portion of the transport service supporting elements affected bythe network event.
 17. The apparatus of claim 16 wherein the indicationunit is made to indicate a subject transport service supporting elementand transport service supporting elements related to the subjecttransport service supporting element affected by the network event; andwherein the visual cue unit is made to provide a visual cue of thenetwork event affecting the transport service in terms of both thesubject supporting element and the supporting elements related to thesubject supporting element affected by the network event.
 18. Theapparatus of claim 16 wherein the indication unit is made to indicate asubject transport service supporting element and transport servicesupporting elements downstream of the subject transport servicesupporting element affected by the network event; and wherein the visualcue unit is made to provide a visual cue of the network event affectingthe transport service in terms of both the subject supporting elementand the supporting elements downstream of the subject supporting elementaffected by the network event.
 19. A computer program product comprisinga computer usable medium embodying computer usable code to correlatevisually a network event affecting a transport service with thetransport service affected by the network event, the computer programproduct including computer usable program code, which when executed by aprocessor, causes the processor to: representing a transport servicebetween point A and point Z in a network in terms of physical networkelements, network entities within the physical network elements, andconnections between the network entities to form a representation of thetransport service, the formed transport service representing a networkevent affecting the transport service to form a representation of thenetwork event; and simultaneously presenting the network eventrepresentation against the transport service representation to provide avisual presentation of the network event affecting the transport servicein terms of the affected physical network elements, network entities,and connections, the provided visual presentation enabling a viewer tocorrelate in a visual manner the network event affecting the transportservice with the transport service affected by the network event.